How a $60M Home Goods Brand Treated a Flipbook Like a Mini-App and Changed Their Q3 Results
In spring 2026 Hearth & Co., a home goods retailer with roughly $60 million in annual revenue and an 8-person digital marketing team, was wrestling with a common problem: their beautifully designed digital catalogs lived on the web and performed like brochures - pretty but forgettable. The team spent $120,000 per year creating seasonal flipbooks and interactive brochures via Publuu, expecting web embeds and email links to drive discovery and conversions. Engagement was low: average read-through rate hovered around 8%, click-throughs to product pages were 1.2%, and the catalogs generated roughly 230 marketing-qualified leads per quarter.
Publuu had launched a branded Android app feature earlier that year allowing enterprise customers to publish native, branded flipbook apps in Google Play, complete with push notifications, offline reading, and native analytics. The Hearth & Co. team assumed a native app would be overkill. They believed web-first distribution was cheaper, easier to maintain, and good enough. That belief turned out to be the thing they were wrong about.
Why the Team Assumed a Web-Only Flipbook Would Be Enough
Hearth & Co.'s assumptions were rooted in practical concerns. The team had run A/B tests showing the web flipbook looked fine on mobile browsers. They were worried about extra costs, app approvals, and the burden of asking users to download yet another app. Senior marketers argued that users find content through email, social, and search, not a standalone app. Their vendor — Publuu — had marketed strong embed tools, which reinforced the web-first stance.
Still, the team faced three stubborn problems that a web flipbook couldn't solve:
- Discoverability outside owned channels: organic reach depended on email lists and a few sponsored posts. New audiences were expensive to reach. Engagement depth: web flipbooks were passive. Time-on-content and repeat visits were low. Measurement and activation: the team wanted event-level data feeding their CRM and the ability to nudge readers with timely offers.
Those unmet needs pushed Hearth & Co. to pilot Publuu’s branded Android app despite initial skepticism.
Why a Native App Made Strategic Sense for This Flipbook Use Case
Choosing a native app was not a stylistic decision. The team mapped three potential gains, treating the app like a channel strategy rather than a new deliverable:
- Push notifications as a re-engagement lever for readers who had already shown interest. Offline access for customers in rural markets with spotty connectivity, reducing churn during browsing. Tighter analytics integration so reading behavior could trigger CRM actions and paid-retargeting audiences.
Publuu’s branded Android app feature promised those abilities out of the box: single-package publishing, a white-label Play Store listing, built-in push notifications, and API hooks for analytics. The vendor’s sales deck hinted at 2-3x engagement lifts, which sounded optimistic. Hearth & Co. negotiated a controlled pilot: $24,000 initial setup and a monthly platform fee of $2,000 for six months, with clear deliverables and a rollback plan if metrics didn’t improve.
Rolling Out the Branded App: A 90-Day Timeline and Milestones
Week 0-2 — Planning and KPI Alignment
The marketing lead aligned stakeholders and set measurable goals: grow catalog read-through rate from 8% to 30% within 6 months, triple flipbook-to-product click-through rate, and cut cost per lead (CPL) from $54 to under $25. Tech set integration priorities: publish events to Google Analytics 4, push flipbook events to the CRM, and enable Firebase for push performance reporting.
Week 3-5 — Content Repackaging and App UI
The team repurposed the spring catalog into an app-native experience. Key changes included modular navigation for sections, product hotspots that open deep links, and a persistent “save for later” feature. Designers treated the flipbook as a native micro-site rather than a static PDF. The UX goal was to make the catalog feel like a mini storefront that fits on a phone screen.
Week 6-8 — Technical Integration and Testing
Developers used Publuu’s API to connect flipbook events (page opens, hotspot clicks, saves) into the CRM, and set up event-driven push campaigns via Firebase. QA focused on offline reads, ensuring previously viewed pages cached correctly and that deep links launched product pages in the main commerce app or mobile web when present. They also tested Play Store submission, privacy disclosures, and in-app consent screens to comply with data rules.
Week 9-12 — Soft Launch and Iteration
Hearth & Co. executed a staged rollout. First, an internal launch to 120 employees and high-intent customers via invite code. Second, a controlled external release to a 10,000-person segment from the loyalty program. They collected feedback, adjusted push timing, trimmed large images to speed initial page loads, and tuned the signup flow to reduce friction. After two weeks of iterative fixes, the app went public in Google Play.
From 8% Engagement to 42%: Measurable Results in Six Months
The pilot exceeded the conservative targets in some areas and landed short of vendor claims in others. Here are the headline metrics, tracked over six months:
- App installs: 12,400 organic downloads from Play Store; 3,100 installs from email invites and loyalty promotions. Average read-through rate: rose from 8% on web to 42% inside the app (defined as completing at least 70% of the pages). Flipbook-to-product CTR: increased from 1.2% to 4.6% — roughly 3.8x improvement. Time on catalog: median session length inside the app was 4 minutes 26 seconds, up from 1 minute 12 seconds on mobile web. Lead generation: marketing-qualified leads rose from 230 per quarter to 1,020 per quarter attributable to the app channel. Cost and revenue: CPL fell from $54 to $18 when app-attributed leads were isolated. Hearth & Co. estimated $228,000 incremental revenue within six months tied to the app channel, based on conversion and average order value. User satisfaction: app store rating averaged 4.6 with qualitative feedback praising offline reading and quicker navigation.
Not everything improved evenly. Push notification open rates averaged 16% — lower than hoped — and a small segment reported push fatigue. Also, the first month’s downloads skewed to existing customers; public discovery grew more slowly than the vendor’s aggressive projections.
Three Lessons That Changed How the Team Thinks About Content Channels
The project overturned several assumptions. Here are the three lessons that mattered most.
1. Distribution trumps extra polish
The team believed better content alone would win attention. The app taught them distribution and channel control matter more. Put simply, a great catalog that nobody revisits has less impact than a good catalog delivered into pockets repeatedly. The app acted like a mailbox with a bell - it reminded people the content existed.
2. Native features solve real friction
Offline access and push notifications are not bells and whistles for this audience. In rural markets with slower connections, offline caching cut bounce rates by 28% because users could flip pages without waiting for large images. Push notifications reactivated dormant readers at lower cost than paid acquisition, especially when tied to time-limited offers.
3. Vendor claims are starting points, not guarantees
Publuu’s promise of tripled engagement was directionally accurate but optimistic. The team learned to convert vendor slide claims into experimentable hypotheses with small pilots and measurable acceptance criteria. This reduced risk and forced realistic expectations.
How Your Marketing Team Can Run a Low-Risk Pilot of a Branded Flipbook App
If your team is debating a similar move, here’s a pragmatic blueprint modeled on Hearth & Co.’s rollout. Think of this as a laboratory setup rather than a full migration.
Define a tight hypothesis and clear KPIs
Example hypothesis: “A branded Android flipbook app will increase catalog read-through rate by 3x and reduce CPL by half over six months.” Pick measurable KPIs: installs, read-through rate, flipbook-to-product CTR, MQLs, and CPL. Set a financial threshold for success (e.g., $100k incremental revenue in six months).
Scope a 90-day pilot
Week 1-2: Stakeholder alignment and KPI definition. Week 3-6: Content repackaging and UI tweaks for mobile-first consumption. Week 7-9: Technical integration (analytics, CRM, push), QA, and privacy review. Week 10-12: Soft launch to a controlled cohort, iterate, then public release.Keep costs transparent
Expect initial setup costs in the $15k-35k range depending on integrations and branding assets, and ongoing fees of $1.5k-3k per month for platform access and push infrastructure. Account for internal hours: plan on at least 120 cross-functional hours across marketing, design, and engineering during the pilot.
Measure and attribute carefully
Push flipbook events into your analytics stack. Tie those events to the CRM to flipbook hotspots feature track downstream conversions. Use UTM parameters for marketing-driven installs. If possible, set up control groups — customers who receive the catalog via web only — to isolate app effects.
Plan for tradeoffs
- App maintenance: regular content pushes and periodic updates for Play Store compliance. Push fatigue: cadence matters. Match notifications to real value - offers, restocks, or curated picks. Discovery scaling: organic Play Store discovery is limited. Expect to amplify via email, loyalty programs, and paid ads.
Final Thoughts: Practical Skepticism Pays Off
Hearth & Co. entered the pilot skeptical and left more strategic. The branded Android app did not solve every problem nor did it produce instant viral growth. Still, it converted passive brochures into a reusable channel, produced measurable uplifts, and delivered a clear ROI within six months.
If there’s a single metaphor that fits: the web flipbook was a poster on a wall. The native app was a shopfront on a busy street that the team could open and close, light up at night, and put a sign on when a sale was on. That control changed behaviors.
Before you sign any vendor contract, turn promises into experiments. Publish a narrow, instrumented pilot, measure rigorously, and budget for the ongoing work an app requires. If your goal is repeat engagement and measurable conversion rather than a one-off content piece, the extra lift to go native may be what you thought you didn't need - until you see the numbers.
